System and method for transaction recovery in a multitenant application server environment

ABSTRACT

In accordance with an embodiment, described herein is a system and method for transaction recovery in a multitenant application server environment. At least one resource manager associated with a partition can be designated as a determiner resource for that partition only, in order to support eliminating transaction logs (TLOG) in processing a two-phase commit transaction. A transaction manager can prepare all other resource managers in the mid-tier transactional system before the determiner resource. Furthermore, the transaction manager can rely on the list of outstanding transactions to be committed that is provided by the determiner resource for recovering the transaction. The transaction manager can commit an in-doubt transaction returned from a resource manager that matches the list of in-doubt transactions returned from the determiner resource. Otherwise, the transaction manager can roll back the in-doubt transaction.

CLAIM OF PRIORITY AND CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. Provisional Application titled “SYSTEM AND METHOD FOR TRANSACTION RECOVERY IN A MULTITENANT APPLICATION SERVER ENVIRONMENT”, Application No. 62/055,858, filed Sep. 26, 2014; and is related to U.S. patent application titled “SYSTEM AND METHOD FOR SUPPORTING MULTI-TENANCY IN AN APPLICATION SERVER, CLOUD, OR OTHER ENVIRONMENT”, application Ser. No. 14/601,883, filed Jan. 21, 2015; each of which above applications are herein incorporated by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF INVENTION

Embodiments of the invention are generally related to application servers and cloud environments, and are particularly related to a system and method for transaction recovery in a multitenant application server environment.

BACKGROUND

Application servers generally provide a managed environment within which software applications can be deployed and run. Cloud-based environments allow applications to run within and take advantage of the distributed resources provided by a cloud. Such environments can support large numbers of users or tenants, some of which may have specific requirements that are particular to that user or tenant.

SUMMARY

In accordance with an embodiment, described herein is a system and method for transaction recovery in a multitenant application server environment. At least one resource manager associated with a partition can be designated as a determiner resource manager for that partition, in order to support eliminating transaction logs (TLOG) in processing a two-phase commit transaction. A transaction manager can prepare all other resource managers in the mid-tier transactional system before the determiner resource manager. Furthermore, the transaction manager can rely on the list of outstanding transactions to be committed that is provided by the determiner resource for recovering the transaction. The transaction manager can commit an in-doubt transaction returned from a resource manager that matches the list of in-doubt transactions returned from the determiner resource manager. Otherwise, the transaction manager can roll back the in-doubt transaction.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

FIG. 2 further illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

FIG. 3 further illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

FIG. 4 illustrates a domain configuration for use with an exemplary multi-tenant environment, in accordance with an embodiment.

FIG. 5 further illustrates an exemplary multi-tenant environment, in accordance with an embodiment.

FIG. 6 shows an illustration of a transactional environment, in accordance with an embodiment of the invention.

FIG. 7 shows an illustration of supporting two-phase commit in a transactional middleware machine environment.

FIG. 8 shows an illustration of recovering in-doubt transactions in a transactional middleware machine environment.

FIG. 9 shows an illustration of supporting a strict ordering of two-phase commit (2PC) calls for processing a transaction in a transactional middleware machine environment, in accordance with an embodiment.

FIG. 10 shows an illustration of recovering a global transaction without using a transaction log (TLOG), in accordance with an embodiment.

FIG. 11 shows an illustration of recovering a global transaction without using a transaction log (TLOG) in a multitenant application server environment, in accordance with an embodiment.

FIG. 12 shows an illustration of recovering a transaction without using a transaction log (TLOG), in a multitenant application server environment, in accordance with an embodiment.

FIG. 13 is an illustrative flow chart of transaction recovery in a multitenant application server environment, in accordance with an embodiment.

DETAILED DESCRIPTION

In accordance with an embodiment, described herein is a system and method for transaction recovery in a multitenant application server environment. At least one resource manager associated with a partition can be designated as a determiner resource manager for that partition only, in order to support eliminating transaction logs (TLOG) in processing a two-phase commit transaction. A transaction manager can prepare all other resource managers in the mid-tier transactional system before the determiner resource. Furthermore, the transaction manager can rely on the list of outstanding transactions to be committed that is provided by the determiner resource for recovering the transaction. The transaction manager can commit an in-doubt transaction returned from a resource manager that matches the list of in-doubt transactions returned from the determiner resource manager. Otherwise, the transaction manager can roll back the in-doubt transaction.

Application Server (e.g., Multi-Tenant, MT) Environment

FIG. 1 illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

As illustrated in FIG. 1, in accordance with an embodiment, an application server (e.g., multi-tenant, MT) environment 100, or other computing environment which enables the deployment and execution of software applications, can be configured to include and operate according to a domain 102 configuration that is used at runtime to define an application server domain.

In accordance with an embodiment, the application server can include one or more partitions 104 that are defined for use at runtime. Each partition can be associated with a globally unique partition identifier (ID) and partition configuration, and can further include one or more resource groups 124, together with a reference to a resource group template 126 and/or partition-specific applications or resources 128. Domain-level resource groups, applications and/or resources 140 can also be defined at the domain level, optionally with a reference to a resource group template.

Each resource group template 160 can define one or more applications A 162, B 164, resources A 166, B 168, and/or other deployable applications or resources 170, and can be referenced by a resource group. For example, as illustrated in FIG. 1, resource group 124 in partition 104 can reference 190 resource group template 160.

Generally, a system administrator can define partitions, domain-level resource groups and resource group templates, and security realms; while a partition administrator can define aspects of their own partition, for example, by creating partition-level resource groups, deploying applications to the partition, or referencing specific realms for the partition.

FIG. 2 further illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

As illustrated in FIG. 2, in accordance with an embodiment, a partition 202 can include, for example, a resource group 205 which includes a reference 206 to a resource group template 210, a virtual target (e.g., virtual host) information 207, and a pluggable database (PDB) information 208. A resource group template (e.g., 210) can define, for example, a plurality of applications A 211 and B 212, together with resources such as a Java Message Server (JMS) server 213, store-and-forward (SAF) agent 215, mail session component 216, or Java Database Connectivity (JDBC) resource 217.

The resource group template illustrated in FIG. 2 is provided by way of example; in accordance with other embodiments, different types of resource group templates and elements can be provided.

In accordance with an embodiment, when a resource group within a partition (e.g., 202) references 220 a particular resource group template (e.g., 210), information associated with a particular partition can be used in combination with the referenced resource group template, to indicate a partition-specific information 230, for example a partition-specific PDB information. The partition-specific information can then be used by the application server to configure resources, for example a PDB resource, for use by the partition. For example, partition-specific PDB information associated with partition 202 can be used, by the application server, to configure 232 a container database (CDB) 236 with an appropriate PDB 238, for use by that partition.

Similarly, in accordance with an embodiment, a virtual target information associated with a particular partition can be used to define 239 a partition-specific virtual target 240, for use by the partition, e.g., baylandurgentcare.com, which can then be made accessible via a uniform resource locator (URL), e.g., http://baylandurgentcare.com.

FIG. 3 further illustrates a system for supporting multi-tenancy in an application server, cloud, or other environment, in accordance with an embodiment.

In accordance with an embodiment, a system configuration such as a config.xml configuration file, is used to define a partition, including configuration elements for resource groups associated with that partition, and/or other partition properties. Values can be specified per-partition using property name/value pairs.

In accordance with an embodiment, a plurality of partitions can be executed within a managed server/cluster 242, or a similar environment which can provide access to a CDB 243, and which are accessible via a web tier 244. This allows, for example, a domain or partition to be associated with one or more of the PDBs (of the CDB).

In accordance with an embodiment, each of the plurality of partitions, in this example partition A 250 and partition B 260, can be configured to include a plurality of resources associated with that partition. For example, partition A can be configured to include a resource group 251 which contains an application A1 252, application A2 254, and JMS A 256, together with a datasource A 257 associated with PDB A 259, wherein the partition is accessible via a virtual target A 258. Similarly, partition B 260 can be configured to include a resource group 261 which contains an application B1 262, application B2 264, and JMS B 266, together with a datasource B 267 associated with PDB B 269, wherein the partition is accessible via a virtual target B 268.

While several of the above examples illustrate use of CDB and PDBs, in accordance with other embodiments, other types of multi-tenant or non-multi-tenant databases can be supported, wherein a particular configuration can be provided for each partition, for example through the use of schemas, or the use of different databases.

Resources

In accordance with an embodiment, a resource is a system resource, application, or other resource or object that can be deployed to a domain of the environment. For example, in accordance with an embodiment, a resource can be an application, JMS, JDBC, JavaMail, WLDF, data source, or other system resource or other type of object that can be deployed to a server, cluster, or other application server target.

Partitions

In accordance with an embodiment, a partition is a runtime and administrative subdivision or slice of a domain that can be associated with a partition identifier (ID) and configuration, and can contain applications and/or refer to domain-wide resources through the use of resource groups and resource group templates.

Generally, a partition can contain its own applications, refer to domain wide applications via resource group templates, and have its own configuration. Partitionable entities can include resources, for example JMS, JDBC, JavaMail, WLDF resources, and other components, such as JNDI namespace, network traffic, work managers, and security policies and realms. In the context of a multi-tenant environment, the system can be configured to provide tenant access to the administrative and runtime aspects of partitions associated with a tenant.

In accordance with an embodiment, each resource group within a partition can optionally reference a resource group template. A partition can have multiple resource groups, and each of them can reference a resource group template. Each partition can define properties for configuration data that is not specified in the resource group templates to which the partition's resource groups refer. This enables the partition to act as a binding of deployable resources defined in a resource group template, to specific values for use with that partition. In some cases, a partition can override configuration information specified by a resource group template.

In accordance with an embodiment, a partition configuration, as defined for example by a config.xml configuration file, can include a plurality of configuration elements, for example: “partition”, which contains the attributes and child elements that define the partition; “resource-group”, which contains the applications and resources deployed to the partition; “resource-group-template”, which contains applications and resources defined by that template; “jdbc-system-resource-override”, which contains a database-specific service name, user name, and password; and “partition-properties”, which contains property key values that can be used for macro replacement in resource group templates.

Upon startup, the system can use the information provided by the configuration file to generate partition-specific configuration elements for each resource, from the resource group template.

Resource Groups

In accordance with an embodiment, a resource group is a named, fully-qualified collection of deployable resources that can be defined either at a domain or partition level, and can reference a resource group template. The resources in a resource group are considered fully-qualified in that the administrator has provided all of the information needed to start or connect to those resources, for example the credentials for connecting to a data source, or the targeting information for an application.

A system administrator can declare resource groups at the domain level, or at the partition level. At the domain level, a resource group provides a convenient way to group related resources. The system can manage resources declared in a domain-level resource group the same as ungrouped resources, so that the resources can be started during system start-up, and stopped during system shut-down. An administrator can also stop, start, or remove a resource in a group individually, and can act on all the resources in a group implicitly by operating on the group. For example, stopping a resource group stops all of the resources in the group that are not already stopped; starting the resource group starts any resources in the group that are not already started; and removing the resource group removes all of the resources contained in the group.

At the partition level, a system or partition administrator can configure zero or more resource groups in a partition, subject to any security restrictions. For example, in a SaaS use case, various partition-level resource groups can refer to domain-level resource group templates; while in a PaaS use case, partition-level resource groups can be created that do not refer to resource group templates, but instead represent applications and their related resources that are to be made available within that partition only.

In accordance with an embodiment, resource grouping can be used to group together applications and the resources they use as a distinct administrative unit within the domain. For example, in the medical records (MedRec) application described below, a resource grouping defines the MedRec application and its resources. Multiple partitions can run the same MedRec resource group, each using a partition-specific configuration information, such that the applications that are part of each MedRec instance are made specific to each partition.

Resource Group Templates

In accordance with an embodiment, a resource group template is a collection of deployable resources that are defined at a domain level, that can be referenced from a resource group, and some of the information required to activate its resources may not be stored as part of the template itself, such that it supports the specification of partition level configuration. A domain can contain any number of resource group templates, each of which can include, for example, one or more related Java applications and the resources on which those applications depend. Some of the information about such resources may be the same across all partitions, while other information may vary from one partition to the next. Not all configuration need be specified at the domain level—partition level configuration can instead be specified in the resource group template through the use of macros, or property name/value pairs.

In accordance with an embodiment, a particular resource group template can be referenced by one or more resource groups. Generally, within any given partition, a resource group template can be referenced by one resource group at a time, i.e., not simultaneously by multiple resource groups within the same partition; however, it can be referenced at the same time by another resource group in a different partition. The object containing the resource group, e.g., the domain or partition, can use property name/value assignments to set the value of any tokens in the resource group template. When the system activates a resource group template using a referencing resource group, it can replace those tokens with values set in the resource group's containing object. In some cases, the system can also use statically-configured resource group templates and partitions to generate runtime configuration for each partition/template combination.

For example, in a SaaS use case, the system can activate the same applications and resources multiple times, including once for each partition that will use them. When an administrator defines a resource group template they can use tokens to represent the information that will be supplied elsewhere. For example, the username to use in connecting to a CRM-related data resource can be indicated in the resource group template as \${CRMDataUsername}.

Tenants

In accordance with an embodiment, in a multi-tenant environment, such as a multi-tenant (MT) application server environment, a tenant is an entity that can be represented by, or otherwise associated with, one or more partitions and/or one or more tenant-aware applications.

For example, tenants can represent distinct user organizations, such as different external companies, or different departments within a particular enterprise (e.g., HR and Finance departments), each of which can be associated with a different partition. A tenant globally unique identity (tenant ID) is the association of a particular user, at a particular moment in time, with a particular tenant. The system can derive which tenant a particular user belongs to from the user identity, for example by referring to a user identity store. The user identity enables the system to enforce those actions that a user is authorized to perform, including, but not limited to, which tenant the user may belong.

In accordance with an embodiment, the system enables isolation of the administration and runtime of different tenants from each other. For example, tenants can configure some behaviors of their applications, and resources to which they have access. The system can ensure that a particular tenant cannot administer artifacts belonging to another tenant; and, at runtime, that the applications working on behalf of a particular tenant refer only to resources associated with that tenant, and not to resources associated with other tenants.

In accordance with an embodiment, a tenant-unaware application is one that contains no logic dealing with tenants explicitly, such that any resources that the application uses may be accessible regardless of what user submitted a request to which the application is responding. In contrast, a tenant-aware application includes logic that explicitly deals with tenants. For example, based on a user's identity the application can derive the tenant to which the user belongs and use that information to access tenant-specific resources.

In accordance with an embodiment, the system enables users to deploy applications that are explicitly written to be tenant-aware, so that application developers can obtain the tenant ID of a current tenant. The tenant-aware application can then use the tenant ID to handle multiple tenants that are using a single instance of the application.

For example, the MedRec application, which supports a single doctor's office or hospital, can be exposed to two different partitions or tenants, e.g., a Bayland Urgent Care tenant, and a Valley Health tenant, each of which is able to access separate tenant-specific resources, such as separate PDBs, without changing the underlying application code.

Exemplary Domain Configuration and Multi-Tenant Environment

In accordance with an embodiment, applications can be deployed to a resource group template at the domain level, or to a resource group that is scoped to a partition or scoped to the domain. Application configuration can be overridden using deployment plans specified per-application, or per-partition. Deployment plans can also be specified as part of a resource group.

FIG. 4 illustrates a domain configuration for use with an exemplary multi-tenant environment, in accordance with an embodiment.

In accordance with an embodiment, when the system starts a partition, it creates virtual targets (e.g., virtual hosts) and connection pools, including one for each partition, to respective database instances, according to the provided configuration.

Typically, each resource group template can include one or more related applications and the resources on which those applications depend. Each partition can provide configuration data that is not specified in the resource group templates to which it refers, by providing a binding of the deployable resources in resource group templates to specific values associated with the partition; including, in some cases, overriding certain configuration information specified by the resource group template. This enables the system to activate an application represented by a resource group template differently for each partition, using the property values each partition has defined.

In some instances, a partition may contain resource groups that do not refer to resource group templates, or that directly define their own partition-scoped deployable resources. Applications and data sources that are defined within a partition are generally available only to that partition. Resources can be deployed so that they can be accessed from across partitions using partition:<partitionName>/<resource JNDI name>, or domain:<resource JNDI name>.

For example, a MedRec application can include a plurality of Java applications, a data source, a JMS server, and a mail session. To run the MedRec application for multiple tenants, the system administrator can define a single MedRec resource group template 286, declaring those deployable resources in the template.

In contrast to domain-level deployable resources, the deployable resources declared in a resource group template may not be fully configured in the template, or cannot be activated as-is, since they lack some configuration information.

For example, the MedRec resource group template may declare a data source used by the applications, but it may not specify a URL for connecting to the database. Partitions associated with different tenants, for example, partition BUC-A 290 (Bayland Urgent Care, BUC) and partition VH-A 292 (Valley Health, VH) can reference one or more resource group templates, by each including a MedRec resource group 293, 294 that references 296, 297 the MedRec resource group template. The reference can then be used to create 302, 306, the virtual targets/virtual hosts for each tenant, including a virtual host baylandurgentcare.com 304 associated with the BUC-A partition, for use by the Bayland Urgent Care tenant; and a virtual host valleyhealth.com 308 associated with the VH-A partition, for use by the Valley Health tenant.

FIG. 5 further illustrates an exemplary multi-tenant environment, in accordance with an embodiment. As illustrated in FIG. 5, and continuing the example from above, in which two partitions reference the MedRec resource group template, in accordance with an embodiment, a servlet engine 310 can be used to support a plurality of tenant environments, in this example a Bayland Urgent Care Physician tenant environment 320, and a Valley Health Physician tenant environment 330.

In accordance with an embodiment, each partition 321, 331 can define a different virtual target on which to accept incoming traffic for that tenant environment, and a different URL 322, 332 for connecting to the partition and to its resources 324, 334, including in this example either a bayland urgent care database, or a valley health database respectively. The database instances can use compatible schemas, since the same application code will execute against both databases. When the system starts the partitions, it can create the virtual targets and connection pools to the respective database instances.

Transactional Environment and Global Transaction

FIG. 6 shows an illustration of a transactional environment, in accordance with an embodiment of the invention. As shown in FIG. 6, a transactional environment 600 can include an application program 602, one or more transaction managers (TM) 603, a plurality of resource managers (RM) 604-606, and one or more persistence stores, e.g. the database 610.

In accordance with an embodiment of the invention, the application program 602 can specify actions that constitute a transaction. As illustrated, the application program 602 communicates with the transaction manager 603 to begin, commit, or abort a transaction, and the transaction manager 603 can send back the start, end, and disposition of the transaction to the application program 602. Furthermore, the application program 602 can define transaction boundaries for the transaction manager 603, which can exchange transaction information with the plurality of resource managers (RM) 604-606. In addition, the application program 602 can communicate with the plurality of resource managers 604-606 via Embedded Structured Query (SQL) to do work.

The plurality of resource managers 604-606 can provide access to persistence stores, e.g. the database 610 (or databases). In accordance with an embodiment of the invention, the plurality of resource managers 604-606 can implement XA (eXtended Architecture) interfaces to handle database connections and disconnections transparently to persistence stores. The XA interfaces can be based on a specification that describes a protocol for transaction coordination, commitment, and recovery. An XA resource participating in a transaction can comprise an XA resource manager and a backend persistence store.

In accordance with various embodiments of the invention, a transactional system can support a global transaction, which can be executed on more than one server, and is capable of accessing data from more than one resource manager.

A global transaction can be treated as a specific sequence of operations that are characterized by four properties, namely atomicity, consistency, isolation, and durability (ACID). The global transaction can be a logical unit of work where all portions of the transaction either succeed or have no effect. As well, operations are performed that correctly transform the resources from one consistent state to another. Additionally, within a global transaction, intermediate results are not generally accessible to other transactions, although other processes in the same transaction may access the data. As well, effects of a completed sequence of a global transaction are not generally altered by failure.

Furthermore, a global transaction, in accordance with an embodiment, may include several local transactions, each accessing a single resource manager. A local transaction can access a single database or file and can be controlled by the resource manager responsible for performing concurrency control and atomicity of updates at that distinct database. A given local transaction may be either successful or unsuccessful in completing its access.

In accordance with an embodiment, the transaction manager 603 can assign global transaction identifiers (GTRIDs) to the different transactions in transactional environment 600. The transaction manager 603 can monitor the progress of the transaction, and take responsibility for ensuring transaction completion and providing failure recovery. In addition, the transaction manager 603 can communicate with the plurality of resource managers 604-605 via XA interfaces to exchange transaction information, such as sending two-phase commits calls to the resource managers 604-605.

Two-phase Commit (2PC)

A two-phase-commit (2PC) protocol can be used to execute a transaction, such as a loosely-coupled global transaction. The two-phase-commit protocol (2PC) can include a prepare phase and a commit phase. In the prepare phase, a coordinating transaction manager (TM) instructs the participating resource managers (RMs) to take the necessary steps for either committing or aborting the transaction. In the commit phase, the transaction manager (TM) decides whether to commit or abort the transaction, based on the results of the prepare phase.

FIG. 7 shows an illustration of supporting two-phase commit in a transactional middleware machine environment. As shown in FIG. 7, a transactional environment 700 can include a transaction manager 701 that supports the execution of various transactions, and one or more resource managers 702-704 that manage one or more data sources, e.g. a database 705.

For example, the transaction manager 701 can execute a transaction that involves transaction branch A 711, transaction branch B 712, and transaction branch C 713, each of which can be executed against a resource manager 702-704 respectively. If any branch fails in the transaction, the transaction manager 701 can help the resource manager 702-704 decide whether to commit, or roll back, the transaction.

As shown in FIG. 7, the transaction manager 701 can send a prepare instruction to the resource manager 702-704 on all three branches (steps 1, 2, and 3). After the resource managers 702-704 return an “OK” vote (steps 4, 5 and 6), the transaction manager 701 can write a transaction log (TLOG) to the database 705 (step 7).

The transaction log may be written either to files, or to a database, so that the transaction manager 701 can have enough information to recover the transaction if any branch fails during the commit phase.

Then, the transaction manager 701 can instruct the resource manager 702-704 to commit all three branches (steps 8, 9 and 10). The resource manager 702-704 can inform the transaction manager 701 after successfully completing the commit phase (steps 11, 12 and 13).

Transaction Recovery Based on a Transaction Log (TLOG)

In accordance with one embodiment of the invention, a transaction log (TLOG) can store the decisions for committing transactions by a transaction manager. For example, the TLOG can store a resource checkpoint record, which can be persisted by the transaction manager to enable it to track the different participating XA resources.

A transaction can be written in the TLOG when a transaction manager receives a success vote from all transaction branches after the prepare phase. The transaction record in TLOG can include at least a transaction identifier (XID), which further includes a GTRID assigned by a transaction manager, and a local XID assigned by a resource manager where the transaction is executed.

Furthermore, the TLOG can hold records of the state of in-flight transactions that are marked to be committed. The TLOG is beneficial to recover in-doubt transactions, which are transactions that have been prepared but have not yet been committed in a mid-tier transactional system, for example, after a system crash. Without recovering the in-doubt transactions, the system can be in an incorrect and inconsistent state after a crash.

For example, if a system fails during a two-phase commit transaction, the updates to one backend data store may have committed, but the updates to another data store, in the same transaction, may not yet have been instructed to commit, i.e., the data store's updates are still pending. Once the failed parts of the system have been re-started, the data stores holding pending updates may not be able to know whether the updates should be committed or rolled-back.

FIG. 8 shows an illustration of recovering in-doubt transactions in a transactional middleware machine environment. As shown in FIG. 8, the transactional middleware machine environment 800 includes a transaction manager 801, and a plurality of resource managers 802-804, and a persistence store, i.e. a database 805.

The transaction manager 801 can automatically determine whether a global transaction is in-doubt, by reading/referring to the TLOG (step 1). Then, the transaction manager 801 can poll the relevant backend data stores of the participating resource managers 802-804. Each of the participating resource managers 802-804 can return a list of in-doubt transactions, which are the transactions that the transaction manager 801 does not know whether to roll it back or commit (steps 2, 4 and 6).

Furthermore, the transaction manager 801 can match each in-doubt transaction with the TLOG, and proceed to either commit or roll back the in-doubt transactions on different resource managers 802-804 (steps 3, 5 and 7). For example, when an in-doubt transaction appears in the TLOG, an XAResource.commit( ) can be called to commit the in-doubt transaction to a resource manager specified in the TLOG. On the other hand, when a transaction is not in the TLOG, i.e., a commit decision has not been made on the transaction before a crash, an XAResource.rollback( ) can be called to roll it back on a resource manager based on the transaction identifier (XID).

As shown in FIG. 8, a transaction may have been prepared on a resource manager 802 and the system crashes before the resource manager 802 can send the success vote to the transaction manager 801. Then, the transaction manager 801 may not be able to receive a success vote from all transaction branches, and therefore can be unable log the transaction in the TLOG. Accordingly, the transaction manager 801 can roll back all branch transactions on their respective resource managers 802-804. Thus, using such a consistent and predictable transaction recovery approach, a transaction manager can avoid a mixed heuristic completion where some branches are committed and some are rolled back.

Alleviating the Need for Transaction Manager Recovery Logs

In a transactional environment, the need to persist recovery information to stable storage in order to conduct recovery and ensure ACID properties is generally a design requirement of two-phase. However, the need to persist recovery information to stable storage (e.g., TLOG), alongside the actual protocol network calls to resource managers, can inflict performance cost for 2PC transactions. It can also carry a significant asset capacity cost due to the shared file system or database storage necessary for highly-available stable storage as well as administrative cost due to the management of this storage. These costs only escalate in the case of site-wide disaster recovery where (synchronous) replication and management of the same are necessary. In such systems, a database residing near a primary site is accessed from an application server on a secondary active site and this database in turn must be synchronously synced to a secondary/standby site. In this very common case, it is often necessary to communicate across at least two sites (and back again) intentionally separated by a distance and force to stable storage on both of these sites for every single transaction.

For example, a typically 2PC transaction utilizing the XA two-phase logging algorithm can involve the following steps. The application can use multiple XA resources in a transaction and issues commit for the transaction. The transaction manager can then issue prepare (e.g., XAResource.prepare) on all XA resource participants (e.g., resource managers). The transaction manager can then persist a transaction log to a stable storage (e.g., a database), where the transaction log contains at least the format id and global transaction id of the transaction. After receiving successful (OK) votes from the resource managers, the transaction manager can issue commit (XAResource.commit) on all the XA resource participants. The transaction manager can then (generally lazily, in batches, etc.) purge/delete the transaction record. In the event of failure, the persisted transaction records are matched to the in-doubt transaction IDs returned from XAResource.recover calls made on all involved resource managers and recovery by commit or rollback is conducted accordingly.

In accordance with an embodiment, alleviating the need for transaction manager to record and persist recovery logs can be an optimization that can provide a significant improvement over existing systems by alleviating the need for extra communication and persistence overhead

In accordance with an embodiment of the invention, by using a technique involving strict ordering of two-phase commit calls and the classification of at least one resource participant as a determiner resource of recovery, it is possible to alleviate the need for transaction logs while still providing transaction recovery and ACID properties.

In accordance with an embodiment, a transaction manager can utilize multiple resources in a transaction and issue commit for the transaction. A certain resource of the multiple resources can be configured to be designated as the determiner (also referred to herein as determiner resource and determiner resource manager) of transaction. In the case of a multitenant application server environment, a partition can specify at least one partition specific determiner resource per transaction. If no determiner resource is configured/elected the transaction system can nominate one and persist the determiner resource in a configuration. If no determiner resource is configured in a multitenant application server environment, an application, such as an application associated with an instantiated resource group within a partition, can nominate a partition specific determiner resource and persist this partition specific determiner resource in a configuration.

In accordance with an embodiment, when a group (e.g., combination) of resources, including the resource designated as the determiner resource, are first used, or a new combination of resources is first used in a two-phase transaction, the combination of resources (i.e., combination of resource managers) can be captured and persisted in configuration automatically by the transaction processing subsystem. This configuration persistence occurs just before the first prepare issued for such a transaction. If this configuration change fails the transaction can be rolled back. While not necessary, this can provide further optimization as it reduces the set of resources that require XAResource.recover calls during recovery.

4. In accordance with an embodiment, during a transaction where a resource is designated as the determiner resource and strict ordering is enforced, the transaction manager forgoes any transaction logging. The transaction manager can issue prepare (XAResource.prepare) on all resource participants, preparing the “determiner” resource last. If the prepare call on a resource other than the determiner resource fails, the determiner will not be prepared and the transaction can be rolled back. If a failure occurs during the prepare of the determiner resource, all non-determiner resources can be rolled back, followed by the rollback of the determiner resource.

In accordance with an embodiment, the transaction manager can issue commit on the resources in the transaction only once determiner resource has indicated it has successfully prepared. Then, the transaction manager can issue commit (XAResource.commit) The transaction manager issues XAResource.commit on all XA resource participants, committing the determiner resource last. As with the prepare call, the determiner resource will not commit until all non-determiner resources have successfully committed. A global retry commit can be issued until an abandonment timer expires.

In accordance with an embodiment, in the event of failure, a XAResource.recover scan can be conducted on all non-determiner resources in configuration and the in-doubt transaction IDs are matched to the in-doubt transaction IDs returned from the determiner resource's XAResource.recovery. Recovery by commit can be issued if there is a match (e.g., existing transaction ID) in the determiner resource's list. Alternatively, a rollback can be issued can be issued if a match is not found.

The above-described technique can be described in more details in the following sections.

A Strict Ordering of the Two-Phase Commit (2PC) Calls

In accordance with an embodiment of the invention, the system can eliminate mid-tier transaction logs (TLOGs) in processing a transaction, based on a strict ordering of the two-phase commit calls.

FIG. 9 shows an illustration of supporting a strict ordering of two-phase commit (2PC) calls for processing a transaction in a transactional middleware machine environment, in accordance with an embodiment. As shown in FIG. 9, a transaction 910, such as a global transaction, can be supported in a mid-tier transactional system 900 that includes a transaction manager (TM) 901, a plurality of resource managers (RMs) 902-904. The resource managers (RMs) 902-903 participate in the global transaction 910, and the resource manager 904 does not participate in the global transaction 910. In accordance with an embodiment, the transaction 910 does not span multiple transactional managers.

In accordance with an embodiment, the resource manager 902 can be designated as the determiner resource for the transaction depicted in FIG. 9. This designation can be performed, for example, by the transaction manager, or by a partition, in which situation the determiner resource would be a partition specific determiner resource that is not accessible from another partition. The designation of the resource manager (RM) 902, as the determiner resource, can be persisted in the configuration for the transaction machine environment. When no determiner resource is designated in a transaction in configuration, the transaction manager 901 can nominate a data source as the determiner resource (step 1) and persist it in the configuration. Additionally, the determiner resource 902 can be a resource other than a database, such as a message queue.

Furthermore, whenever a resource is first used or a new combination of resources is first used in processing the two-phase global transaction 910, the new resource or the new combination of resources can be captured and persisted in the configuration, such as a configuration file, automatically by the transaction manager 901. This configuration persistence can occur before the first prepare request is issued for the two-phase transaction. If this configuration change fails, the transaction 910 can be rolled back.

In accordance with an embodiment of the invention, the transaction manager 901 can ensure that the determiner resource, e.g. resource manager 902, is prepared last, and if all resource managers return a vote of okay after the prepare, the transaction manager can also ensure that the determiner resource 902 is committed last among all participating resource managers, for a 2PC transaction 910.

As shown in FIG. 9, the transaction manager 901 can first prepare the resource manager (RM) 903 (step 2), before preparing the determiner resource (step 4). After receiving an OK vote from the participating resource managers (RMs) 902-903 (steps 3 and 5), the transaction manager 901 can commit the resource manager (RM) 903 (step 6), followed by the determiner resource (step 8). The transaction can be completed after the transaction manager 901 receives a success indication from each of the resource managers 902-903 (steps 7 and 9).

By forcing a strict ordering of the commit and prepare calls, the transaction manager 901 can forgo any logging of resources/checkpoints, including writing a TLOG after the prepare phase is handled successfully. The system can improve the performance of the transaction, while allowing the mid-tier transactional system 900 to recover the transaction 910 by retrieving a list of in-doubt transactions from each resource manager, and subsequently recovering all in-doubt transactions without using a transaction log by comparing the list of in-doubt transactions retrieved from each resource manager (e.g., RM 903 in the embodiment depicted in FIG. 9) other than the determiner resource manager (e.g., determiner RM 902 in FIG. 9) with the list of in-doubt transactions retrieved from the determiner resource manager.

Recovering in-doubt transactions can involve comparing a list of in-doubt transactions retrieved from each resource manager other than the determiner resource manager with the list of in-doubt transactions retrieved from the determiner resource manager; and then rolling back the in-doubt transactions which appear in the list of in-doubt transactions retrieved from each resource manager other than the determiner resource manager but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager. By enforcing the strict ordering of the 2PC transaction, the system can recover a failed transaction by comparing the logs of each resource manager with the log of the final, determiner resource manager.

In accordance with an embodiment, because the determiner resource manager is the resource manager last to be prepared, if the determiner resource manager is prepared then all of the preceding resource managers must have been prepared. If the determiner resource has been successfully prepared, the transaction manage then is able to determine that all other resource managers have successfully been prepared, and therefore it is safe to commit the transaction on all resource managers during a recovery. If only some of the resource managers have been prepared, but the determiner resource manager (last in line) has not been prepared, then the transaction manager can determined that the prepare phase did not complete and the transaction must be rolled back during recovery. The analysis relies on only on comparing the in-doubt (prepared but not committed) transactions of the participating resource managers and the determiner resource manager and eliminates the need to use a separate transaction log.

Recovering a Global Transaction Without Using a TLOG

FIG. 10 shows an illustration of recovering a global transaction without using a transaction log (TLOG), in accordance with an embodiment. As shown in FIG. 10, a 2PC transaction 1010, such as a global transaction, can be supported in a mid-tier transactional system 1000 that includes a transaction manager (TM) 1001, a plurality of resource managers (RM) 1002-1004.

When the transaction 1010 needs to be recovered, such as after a failure, the transaction manager 1001 can attempt to recover, e.g. by placing an XA_recover( ) call, on the determiner resource 1002 (step 1). The transaction manager 1001 can receive a list of in-doubt transactions (prepared but not committed transactions) from the determiner resource 1002 (step 2). Furthermore, the transaction manager 1001 can use the list of in-doubt transactions to build/rebuild the global transaction table (GTT) 1006 (step 3).

In accordance with an embodiment, when the determiner resource 1002 is successfully prepared in the two-phase commit transaction, the list of in-doubt transactions can be identical to mid-tier outstanding transactions that the transaction manager 1001 has instructed the participating resource managers 1002-1003 to commit.

Then, the transaction manager 1001 can attempt to recover, e.g. by placing an XA_recover( ) call, on all the other resource managers in the transactional mid-tier system 1000, including the participating resource manager 1003 (step 9) and the non-participating resource manager 1004 (step 10).

For example, the transaction manager 1001 can receive a list of in-doubt transactions from the participating resource manager 1003 (step 5). The transaction manager 1001 can match the in-doubt transactions in the list with the GTT 1006 table to generate a recover list (steps 6 and 7). Then, the transaction manager 1001 can recover the participating resource manager 1003 based on the recover list (step 8). For example, the transaction manager 1001 can commit the in-doubt transactions that match the GTT 1006 table, and can roll back the in-doubt transactions that do not match the GTT 1006 table.

The above procedures can be performed on the resource manager 1004, which is a non-participating resource. As illustrated in FIG. 10, after placing an XA_recover( ) call on the resource manager 1004, the transaction manager 1001 can receive a list of in-doubt transactions (step 11), which can be matched with the GTT 1006 to generate a recover list (step 12). Then, the transaction manager 1001 can commit/rollback the in-doubt transactions on the resource manager 1004 (steps 14 and 15).

Once all the other resource managers 1003-1004 are recovered (steps 9 and 15), the transaction manager 1001 can commit all transactions in the list of prepared transactions to the determiner resource manager (steps 16 and 17). Finally, transaction manager 1001 can remove the entries in the GTT 1006 (step 18).

In accordance with an embodiment, a transaction from the list of in-doubt transactions cannot be committed to the determiner resource manager 1002 until all other resource managers 1003-1004 have been recovered, even if one or more resource managers are not part of the transaction.

In accordance with an embodiment, the transaction manager 1001 can have knowledge of the participating resources 1002, 1003 of the transaction and additional information about the participating resources 1002, 1003 can be passed along and persisted to the determiner resource 1002 in the prepare phase. With the additional information, the transaction manager 1001 can commit the transactions in the list of in-doubt transactions returned from the determiner resource manager 1002, without waiting for all known resource managers 1002-1004 to recover. The transaction manager 1001 may only need to wait until all participants of the transaction, i.e., determiner resource manager 1002 and resource manager 1003, are recovered. Additionally, during a clean shutdown or restart of the transactional mid-tier system 1000, the configuration can be purged or marked, in such a way that unnecessary recovery and processing may be avoided during startup.

Recovering a Transaction Without Using a TLOG in a Multitenant Environment

FIG. 11 shows an illustration of recovering a global transaction without using a transaction log (TLOG) in a multitenant application server environment, in accordance with an embodiment.

In accordance with an embodiment, a plurality of partitions can be executed within a managed server/cluster 242, or a similar environment which can provide access to a CDB 243, and which are accessible via a web tier 244. This allows, for example, a domain or partition to be associated with one or more of the PDBs (of the CDB).

In accordance with an embodiment, each of the plurality of partitions, in this example partition A 250 and partition B 260, can be configured to include a plurality of resources and resource managers associated with that partition. For example, partition A can be configured to include a resource group 1120 which contains an application 1121, resource managers 1122, and a partition configured determiner resource manager A 1123, and wherein the partition is accessible via a virtual target A 258. Similarly, partition B 260 can be configured to include a resource group 1130 which contains an application 1131, resource managers 1132, and a partition configured determiner resource manager B 1133, and wherein the partition is accessible via a virtual target A 258. The managed server can additionally include a transaction manager 1110 which can be instantiated into each partition, as shown in the figure as TM 1110′ and 1110″.

In accordance with an embodiment, the system depicted in FIG. 11 can execute a two phase commit transaction utilizing the strict order as described above. For example, instantiated transaction manager 1110′ can issue prepare calls to resources associated with an application executing in the context of partition A 250. A resource manager, resource manager 1123, can have been designated by the partition (e.g., at runtime or via a configuration file) as the determiner resource manager for the transaction. This designation can indicate that the determiner resource manager is a partition specific determiner resource manager, and thus is not accessible from another partition. The designation of the resource manager (RM) 1123, as the determiner resource, can be persisted in the configuration for the transaction machine environment.

In accordance with an embodiment of the invention, the transaction manager 1110′ can ensure that the determiner resource, e.g. determiner resource manager 1123, is prepared last, and if all resource managers return a vote of okay after the prepare, the transaction manager can also ensure that the determiner resource manager 1123 is committed last among all participating resource managers, for a two phase commit transaction.

In accordance with an embodiment, because the determiner resource manager is partition specific, if a transaction within a partition fails, the system can still allow other transactions associated with other partitions to run (even if the determiner resource manager is the same as the determiner resource manager in another partition). Since each determiner resource manager is associated with a specific partition, the system can still have two partitions using the same resource, the system can still allow one partition to run while disallowing another. That is, because of the partition specific determiner resource, a failed transaction at one partition will not necessarily impact another partition running a transaction.

In accordance with an embodiment, the determiner resource managers associated with partitions can be partition specific. Because of this, and due to the fact that a resource can be partition specific, configuration of determiner resources at a partition level can be supported. As partition-specific resources can have their partition name concatenated to the resourcename, there are no issues with duplicate or overriding resource registrations. The can hold true for partitions that use the same resource group template—the resourcenames can be unique and so the determiner specifications remain unique to the partition. For example, partition A may have the same resource group template as partition B, which includes resource resourceA. In such a circumstances, however, partition A may configure resourceA a determiner resource because internally the resourcenames are different, for example, resourceA_partitionA and resourceA_partition B.

FIG. 12 shows an illustration of recovering a transaction without using a transaction log (TLOG), in a multitenant environment, in accordance with an embodiment. As shown in FIG. 12, in accordance with an embodiment, a plurality of partitions can be executed within a managed server/cluster 242, or a similar environment which can provide access to a CDB 243, and which are accessible via a web tier 244. This allows, for example, a domain or partition to be associated with one or more of the PDBs (of the CDB).

In accordance with an embodiment, each of the plurality of partitions, in this example partition A 250 and partition B 260, can be configured to include a plurality of resources associated and resource managers with that partition. The managed server can additionally include a transaction manager 1210 which can be instantiated into each partition, as shown in the figure TM 1210′. Partition A 250 can include resource manager (participant) 1203 and determiner resource manager for partition A 1204.

In accordance with an embodiment, a 2PC transaction can be supported in a multitenant environment that includes a transaction manager (TM) 1210 instantiated in a partition (e.g., TM 1210′), a plurality of resource managers, for example resource managers (RM) 1203-1204. It should be noted that FIG. 12 only shows two resource managers participating in the transaction recovery for simplicity. It should be appreciated that a number of resource managers, both participating and non-participating, can also be included in the system.

When the transaction needs to be recovered, such as after a failure, the transaction manager can attempt to recover, e.g., by placing an XA_recover( ) call, on the determiner resource 1204 (step 1). The transaction manager can receive a list of in-doubt transactions (prepared but not committed transactions) from the determiner resource 1204 (step 2). Furthermore, the transaction manager 1001 can use the list of in-doubt transactions to build/rebuild a transaction table.

In accordance with an embodiment, when the determiner resource 1204 is successfully prepared in the two-phase commit transaction, the list of in-doubt transactions can be identical to mid-tier outstanding transactions that the transaction manager has instructed the participating resource managers 1203 to commit.

Then, the transaction manager can attempt to recover, e.g., by placing an XA_recover( ) call, on all the other resource managers, including the participating resource manager 1203 (step 3).

For example, the transaction manager can receive a list of in-doubt transactions from the participating resource manager 1203 (step 4). The transaction manager can match the in-doubt transactions in the list the transaction table to generate a recover list. Then, the transaction manager can recover the participating resource manager 1203 based on the recover list (step 5), and the resource manager 1203 can return a success (step 6). For example, the transaction manager can commit the in-doubt transactions that match the transaction table, and can roll back the in-doubt transactions that do not match the transaction table.

Once all the other resource managers 1203 are recovered, the transaction manager can commit all transactions in the list of prepared transactions to the determiner resource manager, which can return a success (step 8).

In accordance with an embodiment, a transaction from the list of in-doubt transactions cannot be committed to the determiner resource manager 1204 until all other resource managers have been recovered, even if one or more resource managers are not part of the transaction.

FIG. 13 is an illustrative flow chart of transaction recovery in a multitenant application server environment, in accordance with an embodiment. As shown in FIG. 13, at step 1310, the method can provide, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more resource group templates, which define groupings of deployable resources within a domain, and one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain, that can be associated with a tenant.

At step, 1320, the method can, as described above, operate a transaction manager within the application server environment.

At step 1330, the method can associate a determiner resource manager with one of the one or more partitions. Further, the determiner resource manager can be used in a transaction.

At step 1340, the method can provide a plurality of resource managers, where the plurality of resource managers are also used in the transaction.

At step 1350, transaction manager can process the transaction by sending a prepare message to the determiner resource manager only after receiving acknowledgement of successful prepare actions on the plurality of resource managers, and sending a commit message to the determiner resource manager only after receiving acknowledgement of successful commit actions on the plurality of resource managers.

In the event of a failure, at step 1360, the method can retrieve a list of in-doubt transactions from each of the plurality of resource managers and the determiner resource manager, and then recover all in-doubt transactions without using a transaction log

The present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.

In some embodiments, the present invention includes a computer program product which is a non-transitory storage medium or computer readable medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.

The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents. 

What is claimed is:
 1. A system for transaction recovery in a multitenant application server environment, comprising: one or more computers, including an application server environment executing thereon, together with a plurality of deployable resources which can be used within the application server environment, one or more resource group templates, which define groupings of deployable resources within a domain, and one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain, that can be associated with a tenant; a transaction manager operating in the application server environment; a determiner resource manager, the determiner resource manager being associated with one of the one or more partitions, the determiner resource manager being used in a transaction; and a plurality of resource managers, the plurality of resource managers being used in the transaction; wherein the transaction manager is configured to process the transaction by, sending a prepare message to the determiner resource manager only after receiving acknowledgement of successful prepare actions on the plurality of resource managers, sending a commit message to the determiner resource manager only after receiving acknowledgement of successful commit actions on the plurality of resource managers; and upon a failure, retrieving a list of in-doubt transactions from each of the plurality of resource managers and the determiner resource manager, and recovering all in-doubt transactions without using a transaction log.
 2. The system of claim 1, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 3. The system of claim 1, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 4. The system of claim 1, wherein the determiner resource manager is designated as the determiner resource manager by the one partition of the one or more partitions.
 5. The system of claim 4, wherein the transaction manager persists the designation of the determiner resource manager in a configuration file.
 6. The system of claim 1, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality of resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 7. The system of claim 1, wherein, upon the failure, the system is configured to commit transactions which appear in the list of in-doubt transactions retrieved from the determiner resource manager after recovering all other resource managers in the plurality of resource managers.
 8. A method for transaction recovery in a multitenant application server environment, comprising: providing, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more resource group templates, which define groupings of deployable resources within a domain, and one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain, that can be associated with a tenant; operating a transaction manager within the application server environment; and associating a determiner resource manager with one of the one or more partitions, the determiner resource manager being used in a transaction; and providing a plurality of resource managers, the plurality of resource managers being used in the transaction; wherein the transaction manager is configured to process the transaction by, sending a prepare message to the determiner resource manager only after receiving acknowledgement of successful prepare actions on the plurality of resource managers, and sending a commit message to the determiner resource manager only after receiving acknowledgement of successful commit actions on the plurality of resource managers; and upon a failure, retrieving a list of in-doubt transactions from each of the plurality of resource managers and the determiner resource manager, and recovering all in-doubt transactions without using a transaction log.
 9. The method of claim 8, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 10. The method of claim 8, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 11. The method of claim 8, wherein the determiner resource manager is designated as the determiner resource manager by the one partition of the one or more partitions.
 12. The method of claim 11, wherein the transaction manager persists the designation of the determiner resource manager in a configuration file.
 13. The method of claim 8, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality of resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 14. The method of claim 13, further comprising, upon the failure, committing transactions which appear in the list of in-doubt transactions retrieved from the determiner resource manager after recovering all other resource managers in the plurality of resource managers.
 15. A non-transitory computer readable storage medium, including instructions stored thereon for transaction recovery in a multitenant application server environment which when read and executed by one or more computers cause the one or more computers to perform steps comprising: providing, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more resource group templates, which define groupings of deployable resources within a domain, and one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain, that can be associated with a tenant; operating a transaction manager within the application server environment; and associating a determiner resource manager with one of the one or more partitions, the determiner resource manager being used in a transaction; and providing a plurality of resource managers, the plurality of resource managers being used in the transaction; wherein the transaction manager is configured to process the transaction by, sending a prepare message to the determiner resource manager only after receiving acknowledgement of successful prepare actions on the plurality of resource managers, and sending a commit message to the determiner resource manager only after receiving acknowledgement of successful commit actions on the plurality of resource managers; and upon a failure, retrieving a list of in-doubt transactions from each of the plurality of resource managers and the determiner resource manager, and recovering all in-doubt transactions without using a transaction log.
 16. The non-transitory computer readable storage medium of claim 15, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 17. The non-transitory computer readable storage medium of claim 15, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; and committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager.
 18. The non-transitory computer readable storage medium of claim 15, wherein the determiner resource manager is designated as the determiner resource manager by the one partition of the one or more partitions.
 19. The non-transitory computer readable storage medium of claim 18, wherein the transaction manager persists the designation of the determiner resource manager in a configuration file.
 20. The non-transitory computer readable storage medium of claim 15, wherein recovering all in-doubt transactions without using a transaction log comprises: comparing the list of in-doubt transactions retrieved from each of the plurality of resource managers with the list of in-doubt transactions retrieved from the determiner resource manager; committing one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality of resource managers and which also appear in the list of in-doubt transactions retrieved from the determiner resource manager; and rolling back one or more in-doubt transactions which appear in the list of in-doubt transactions retrieved from each of the plurality resource managers but do not appear in the list of in-doubt transactions retrieved from the determiner resource manager. 